Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DB migration scripts fixed for PostgreSQL, MSSQL and DB2 #1061

Merged

Conversation

StefanKlt
Copy link
Contributor

There is a bug in the database migration scripts version 1_12_16 for PostgreSQL, Microsoft SQL Server and DB2.
The script for DB2 does not work, the scripts for PostgreSQL and Microsoft SQL Server only work if the sp_action table is empty. The reason is that a column was added that does not allow a null value, which results in an error.
To fix that a default value was added to the column. The default value is an empty string and the default is removed from the column after is is created. That way we get the same behaviour that we have when using MySQL.

Signed-off-by: Stefan Klotz <stefan.klotz@bosch.io>
Signed-off-by: Stefan Klotz <stefan.klotz@bosch.io>
Signed-off-by: Stefan Klotz <stefan.klotz@bosch.io>
Copy link
Contributor

@bogdan-bondar bogdan-bondar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks a lot for the fix Stefan!

@schabdo schabdo added this to the 0.3.0M7 milestone Dec 22, 2020
@schabdo schabdo merged commit ba2b3a6 into eclipse-hawkbit:master Feb 8, 2021
@schabdo schabdo deleted the fix_database_migration_scripts branch February 8, 2021 09:17
@schabdo schabdo added the bug label Feb 8, 2021
@schabdo schabdo changed the title Fix database migration scripts DB migration scripts fixed for PostgreSQL, MSSQL and DB2 Feb 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants